[connection-callback] Introduce a Report Retry timeout for hotplug events in HIDRAW#765
Closed
k1-801 wants to merge 1 commit intolibusb:connection-callbackfrom
Closed
[connection-callback] Introduce a Report Retry timeout for hotplug events in HIDRAW#765k1-801 wants to merge 1 commit intolibusb:connection-callbackfrom
k1-801 wants to merge 1 commit intolibusb:connection-callbackfrom
Conversation
Member
|
Somehow Arch Linux build failed again, but not related to this PR. error: target not found: libudev0 This needs to be changed to libudev0-shim. |
Member
|
Windows cmake build failed as well, again, nothing to do with this PR. |
Author
|
Testing revealed that the issue was somehow caused by the library being loaded through Building the aplication with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fix targets the scenario when
udevreported a new device, but the device is not yet ready to provide a report. This results in the independentusageentries not generating for the device and certain fields in the device not being filled.UPD: The patch, despite potentially solving timing related issues, proved to not be enough to solve the particular problem at hand, investigation continues. Marking as draft, going to update it in the next week.